-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add "server-room.md" Page to the Operations Basics Section #31
base: master
Are you sure you want to change the base?
Conversation
为运维基础部分添加了一个新的页面,介绍了机房的相关信息。
|
i got it , thanku |
更新了机柜规格页面,添加了对机柜尺寸、宽度、高度和深度的详细说明,并介绍了机柜的其他小细节,如螺丝螺母标准、通风设计、电源管理和线缆管理。
Could someone please review the section I wrote about rack to see if it meets your expectations? Additionally, if there are any corrections or improvements needed, I would appreciate your feedback |
Please configure with https://github.com/ustclug/Linux201-docs?tab=readme-ov-file#%E6%A0%BC%E5%BC%8F%E6%A3%80%E6%9F%A5 instructions locally first -- currently CI would not report PR status correctly: > autocorrect --lint
..............................................
docs/ops/server-room/rack.md:18:1
-机柜的宽度通常固定为19英寸(约48.26厘米),这一标准源于 EIA-310-D 标准(Electronic Industries Alliance),该标准在数据中心和 IT 设备安装中得到了广泛应用。
+机柜的宽度通常固定为 19 英寸(约 48.26 厘米),这一标准源于 EIA-310-D 标准(Electronic Industries Alliance),该标准在数据中心和 IT 设备安装中得到了广泛应用。
docs/ops/server-room/rack.md:26:1
-高度以U为单位进行测量(1U = 1.75英寸),这使得不同制造商生产的设备可以轻松兼容和安装到同一机架中。
+高度以 U 为单位进行测量(1U = 1.75 英寸),这使得不同制造商生产的设备可以轻松兼容和安装到同一机架中。
docs/ops/server-room/rack.md:30:1
-机柜的深度根据安装需求可变,常见的深度范围从600mm到1200mm。
+机柜的深度根据安装需求可变,常见的深度范围从 600mm 到 1200mm。
docs/ops/server-room/rack.md:38:1
-机柜安装时通常使用标准化的螺母和螺钉。最常见的螺母类型是方形螺母和M6螺母,这些螺母与标准机架配合使用,确保设备的稳固安装。
+机柜安装时通常使用标准化的螺母和螺钉。最常见的螺母类型是方形螺母和 M6 螺母,这些螺母与标准机架配合使用,确保设备的稳固安装。
docs/ops/server-room/rack.md:46:1
-机柜内通常安装有电源分配单元(PDU),这些PDU提供多种电源插座配置,支持不同类型的设备电源需求。部分PDU还配备有电流监控和断路器功能,可以更好地管理电力分配,防止过载情况的发生。
+机柜内通常安装有电源分配单元(PDU),这些 PDU 提供多种电源插座配置,支持不同类型的设备电源需求。部分 PDU 还配备有电流监控和断路器功能,可以更好地管理电力分配,防止过载情况的发生。
Error: 5, Warning: 0
AutoCorrect spend time: 60.534ms
> markdownlint-cli2 docs/**/*.md README.md
...
docs/ops/server-room/other.md:15:6 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
docs/ops/server-room/other.md:15:6 MD047/single-trailing-newline Files should end with a single newline character |
docs/ops/server-room/rack.md
Outdated
|
||
## 机柜的其他小细节 {#additional-rack-details} | ||
|
||
### 螺丝螺母的标准 {#screw-nut-standards-rack} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Short sentences of introduction for each part could be written in this format:
Linux201-docs/docs/ops/storage/intro.md
Lines 161 to 185 in 0891eb4
RAID 0 | |
: 也称作条带化(Striped),将数据分块存储在多个磁盘上,可以充分利用所有容量,获得叠加的顺序读写性能(但随机读写性能一般),但没有冗余,任何一块磁盘损坏都会导致整个阵列的数据丢失,适合需要高性能读写但不需要数据安全性的场景。 | |
RAID 1 | |
: 也称作镜像(Mirrored),将数据完全复制到多个磁盘上,提供了绝对冗余,整个阵列中只需要有一块盘存活,数据就不会丢失。代价是整个阵列的容量等单块磁盘的容量,空间利用率低下,适合需要高可靠性<s>而且不缺钱</s>的场景。同时由于每块盘上的数据完全一致,RAID 1 的读取性能可以叠加(甚至包括随机读取),但写入性能不会提升。 | |
RAID 5 | |
: 将数据和**一份**校验信息分块存储在多个磁盘上,可以允许阵列中任何一块磁盘损坏,兼顾冗余性和容量利用率。重建期间的性能会严重下降,并且一旦在重建完成前又坏了一块盘,那么你就寄了。 | |
!!! danger "不要为大容量机械硬盘阵列组 RAID 5" | |
否则坏了一块盘后重建的时候就等死吧。 | |
下面的思考题也会涉及到这个问题。 | |
RAID 6 | |
: 将数据和**两份**校验信息分块存储在多个磁盘上,比 RAID 5 多了一份校验信息,可以容纳两块磁盘损坏,适合大容量或者磁盘较多的阵列。尽管允许两块盘损坏,但我们仍然建议在第一块盘损坏后立即更换并重建,不要等到更危险的时候。 | |
RAID 10, 50, 60 | |
: 将不同级别的 RAID 组合在一起,兼顾性能和冗余,各取所长,对于 10 块盘以上的阵列是更加常见的选择。例如 RAID 10 = RAID 1 + RAID 0,通常将每两块盘组成 RAID 1,再将这些 RAID 1 的组合拼成一个大 RAID 0。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the Python Markdown syntax for HTML <dl>
(definition lists) - suits here perfectly:
https://squidfunk.github.io/mkdocs-material/reference/lists/#using-definition-lists
Description:
I have created a new page named
server-room.md
for the Operations Basics section, which aims to introduce basic information about small-scale data centers. This page is intended to provide Linux201 project users with essential foundational knowledge about data centers. The main content includes:Discussion Points:
Can we clarify the focus of the existing
server.md
section? Should it cover detailed types of physical servers, like blade, tower, and rack servers? We need to discuss howserver.md
andserver-room.md
should relate to each other to ensure consistent and logical content organization.